Versions:

  • 0.5.0
  • v0.9.5
  • v0.9.4
  • v0.9.3
  • v0.9.2
  • v0.9.1
  • v0.9.0
  • v0.8.5
  • v0.8.4
  • v0.8.3
  • v0.8.1
  • v0.7.0
  • v0.6.1
  • v0.6.0
  • v0.5.2
  • v0.5.1
  • v0.33.0
  • v0.32.0
  • v0.31.0
  • v0.30.1
  • v0.30.0
  • v0.29.4
  • v0.29.3
  • v0.29.2
  • v0.29.1
  • v0.29.0
  • v0.28.2
  • v0.28.1
  • v0.28.0
  • v0.27.0
  • v0.26.1
  • v0.26.0
  • v0.25.0
  • v0.24.1
  • v0.24.0
  • v0.23.3
  • v0.23.2
  • v0.23.1
  • v0.23.0
  • v0.22.0
  • v0.21.0
  • v0.20.3
  • v0.20.2
  • v0.20.1
  • v0.20.0
  • v0.19.0
  • v0.18.2
  • v0.18.1
  • v0.18.0
  • v0.17.0
  • v0.16.0
  • v0.15.5
  • v0.15.4
  • v0.15.3
  • v0.15.2
  • v0.15.1
  • v0.15.0
  • v0.14.2
  • v0.14.1
  • v0.14.0
  • v0.13.4
  • v0.13.2
  • v0.13.1
  • v0.13.0
  • v0.12.0
  • v0.11.0
  • v0.10.0

worktrunk 0.5.0, released by max-sixty as the 62nd iteration of the project, is a command-line Git worktree manager purpose-built for teams that follow trunk-based development. Instead of juggling stashes or repeatedly mutating a single working directory, developers invoke the short wt command to spawn, swap among, and retire linked worktrees that all share one local repository object database. The tool targets software engineers who need to review, build, and test several topic branches concurrently while keeping a clean, always-updatable trunk copy on disk; typical use cases include parallel pull-request validation, hot-fix rehearsal, and continuous integration staging without CI configuration changes. By automating worktree path allocation and branch tracking, worktrunk eliminates manual folder bookkeeping and reduces context-switching overhead, letting users move straight into compiling, linting, or running test suites inside each isolated tree. Written in a portable systems language and distributed as a single executable, it integrates transparently with existing Git aliases, shell completion scripts, and IDE terminal panes, so teams can adopt it without altering established trunk-based policies or server-side hooks. The utility surfaces only the subset of Git worktree operations that matter for short-lived feature branches, hiding incidental flags and offering opinionated defaults that keep the number of active trees predictable and disk usage low. Because every worktree is a full working copy, developers can run independent build caches, node_modules folders, or Docker contexts side-by-side, confident that changes in one tree will not pollute another. worktrunk is available for free on get.nero.com, with downloads provided via trusted Windows package sources such as winget, always delivering the latest version and supporting batch installation of multiple applications.

Tags: